Release 10.1A: OpenEdge Data Management:
Database Administration

OpenEdge Structure Statistics utility

Use the Structure Statistics utility (PROSTRCT STATISTICS) to monitor database growth and the availability of free blocks for storing additional data. For example:

prostrct statistics db-name

You specify the database whose storage information you want and the PROSTRCT STATISTICS utility displays information about:

The database name.
The primary database block size and the before-image and after-image block sizes.
The storage area and each extent within it.
The total number of active blocks allocated for each data area.
The total number of empty blocks in each data area.
The total number of extent blocks for each data area.
The total number of blocks for each data area.
The total records per block for each data area.
The total number of all blocks (active, data, free, empty, extent, and total blocks).
The date and time of the last full database backup.

Running PROSTRCT STATISTICS against an online database gives you a snapshot of the database state at that moment in time.

For example, this command displays the PROSTRCT STATISTICS command and part of the database storage information output for the database /usr1/doc/sample.db:

$ prostrct statistics sample WARNING: Before-image file of database sample is not truncated. (1552) The last backup was not completed successfully. (1553) Storage Utilization Statistics Database: sample Primary data block size: 1024 BI block size: 8192 AI block size: 8192 Database Phyical structure information Statistics for Area: Control Area Files in Area: Control Area /usr1/doc/sample.db 32768 Database Block Usage for Area: Control Area Active blocks: 6 Empty blocks: 26 Extent blocks: 1 Total blocks: 32 Records/Block: 32 Statistics for Area: Primary Recovery Area Files in Area: Primary Recovery Area /usr2/doc_bi/sample.b1 31064064 Statistics for Area: Schema Area Files in Area: Schema Area /usr1/doc/sample.d1 950272 Database Block Usage for Area: Schema Area Active blocks: 884 Empty blocks: 44 Extent blocks: 1 Total blocks: 928 Records/Block: 32

Statistics for Area: Employee Files in Area: Employee /usr1/doc/sample_7.d1 327680 /usr1/doc/sample_7.d2 32768 Database Block Usage for Area: Employee Active blocks: 28 Empty blocks: 324 Extent blocks: 2 Total blocks: 352 Records/Block: 32      .      .      . Statistics for Area: After Image Area 1 Files in Area: After Image Area 1 /usr3/doc_ai/sample.a1 524288 Statistics for Area: After Image Area 2 Files in Area: After Image Area 2 /usr3/doc_ai/sample.a2 524288 Statistics for Area: After Image Area 3 Files in Area: After Image Area 3 /usr3/doc_ai/sample.a3 93454336 Statistics for Area: Audit Area Files in Area: Audit Area /usr1/doc/sample_20.d1 3440640 Database Block Usage for Area: Audit Area Active blocks: 3311 Empty blocks: 49 Extent blocks: 1 Total blocks: 3360 Records/Block: 32 Statistics for Area: Audit Index Files in Area: Audit Index /usr1/doc/sample_22.d1 1540096

Database Block Usage for Area: Audit Index Active blocks: 1459 Empty blocks: 45 Extent blocks: 1 Total blocks: 1504 Records/Block: 32 Database Block Usage Summary Active blocks: 8320 Data: 8141 Free: 179 Empty blocks: 1184 Extent blocks: 16 Total blocks: 9504 Last full database backup on Tue Sep 13 15:28:07 2005. (6942)

If a full backup has not yet been performed against service.db, the message would read “NO FULL BACKUP HAS BEEN DONE.”